Methods, systems and computer program products for synthesizing diagnoses in healthcare databases

ABSTRACT

Methods, systems and computer program products for synthesizing diagnoses stored in healthcare databases are provided. A diagnosis query associated with a single patient or a group of patients is received. Query results are provided responsive to the diagnosis query. The query results may include diagnoses from multiple sources that are expressed in multiple standards formats.

FIELD OF THE INVENTION

The invention relates to database management in general and, more particularly, to synthesizing to data stored in databases.

BACKGROUND OF THE INVENTION

As the field of healthcare continues to become more specialized, the provision of services by many healthcare workers and/or providers to one patient and/or many patients may increase. In order to accomplish this, healthcare delivery has been organized into specialized departments or healthcare sources such as, for example, nursing, laboratory, pharmacy, and radiology departments. Each department has the responsibility for accomplishing its particular, often specialized, subset of tasks. Sometimes the departments are associated with different healthcare enterprises or offices having different geographic locations. Unfortunately, this has resulted in sub-optimal healthcare operations because patient information related to a single patient that is stored at various departments may not be easily accessible from a single place.

This patient information, or medical data, may be stored in a database environment configured to store large volumes of data. Furthermore, the medical data stored in the database environment may be processed by, for example, searching the stored medical data. Details with respect to conventional methods for storing and/or accessing medical data in and/or from databases is discussed in, for example, United States Patent Publication Nos. US 2003/0088438 and US 2003/0177132.

The patient information, for example, diagnoses, may be stored using one of many standards, such as ICD9, ICD 10, SNOMED, LOINC and the like. Thus, synthesizing this patient information into coherent pictures may be difficult because the same information may be called something different in each database. Furthermore, as the amount of available medical data expands, it may become increasingly difficult to synthesize the medical data, especially for research and comparison purposes. For example, use of the medical data for purposes of diagnosing various medical conditions and/or researching medical areas may be very difficult.

SUMMARY OF THE INVENTION

Some embodiments of the present invention provide methods, systems and computer program products for synthesizing diagnoses stored in healthcare databases. A diagnosis query associated with a single patient or a group of patients is received. Query results are provided responsive to the diagnosis query. The query results may include diagnoses from multiple sources that are expressed in multiple standards formats.

In further embodiments of the present invention a username and password associated with the username may be verified. In these embodiments, the diagnosis query may only be received if the username and password are verified. Each username and associated password may be associated with a level of security clearance. The level of security clearance may determine which information can be accessed by a user of the associated username and password.

It still further embodiments of the present invention, it may be determined if the diagnosis query includes a first standards code in conformance with a first standard therein. Equivalent standards codes to the first standards code in conformance with at least one second standard, different from the first standard, may be determined if it is determined that the diagnosis query includes a first standards code. The query results may be provided based on both the first standards code and the equivalent standards codes.

In some embodiments of the present invention, query adjustments may be received responsive to the provided query results. Future query results may be adjusted based on the received query adjustments. The received diagnosis query may include a discrete query or a semantic query.

In further embodiments of the present invention, the received diagnosis query may be processed to generate at least one modified diagnosis query that can be provided to external databases to obtain the query results. The at least one modified diagnosis query may be provided to at least one standards database and/or at least one diagnostic test results database. Intermediate query results may be received from the at least one standards database and/or the at least one diagnostic test results database. A format of the intermediate query results may be modified before the query results are provided to a user. The format may be modified based on a user profile and/or information obtained from previously received diagnosis queries.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating data processing systems according to some embodiments of the present invention.

FIG. 2 is a block diagram illustrating an exemplary network environment for operations and devices according to some embodiments of the present invention.

FIG. 3 is a block diagram illustrating data flows of a system including a healthcare query module according to some embodiments of the present invention.

FIGS. 4 through 6 are flowcharts illustrating operations according to various embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

The invention now will be described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As will be appreciated by one of skill in the art, the invention may be embodied as a method, data processing system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium. Any suitable computer readable medium may be utilized including hard disks, CD-ROMs, optical storage devices, a transmission media such as those supporting the Internet or an intranet, or magnetic storage devices.

Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java®, Smalltalk or C++. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or in a visually oriented programming environment, such as VisualBasic.

The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The invention is described in part below with reference to flowchart illustrations and/or block diagrams of methods, systems, computer program products and data structures according to embodiments of the invention. It will be understood that each block of the illustrations, and combinations of blocks, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the block or blocks.

Embodiments of the present invention will now be discussed with respect to FIGS. 1 through 6. As discussed herein, some embodiments of the present invention provided methods, systems and computer program products for synthesizing diagnoses of one or more patients. The diagnoses may be stored in healthcare databases in different locations. In particular, a researcher or medical personnel may provide a diagnosis query associated with a single patient or a group of patients to a healthcare query module according to some embodiments of the present invention. As used herein, a “diagnosis query” may include any information related to medical diagnoses of a single patient or group of patients for medical and/or research purposes. According to some embodiments of the present invention, query results may be provided, responsive to the diagnosis query. The query results may include synthesized diagnoses for one or more patients from multiple diagnostic sources that are expressed in multiple standards formats as will be discussed further below with respect to FIGS. 1 through 6.

Referring now to FIG. 1, an exemplary data processing system 100 or healthcare query module/database environment that may be included in devices operating in accordance with some embodiments of the present invention will be discussed. As illustrated, the data processing system 100 includes a processor 138, a memory 136 and input/output circuits 146. The data processing system 100 may be incorporated in, for example, a personal computer, server, router or the like. The processor 138 communicates with the memory 136 via an address/data bus 148 and communicates with the input/output circuits 146 via an address/data bus 149. The input/output circuits 146 can be used to transfer information between the memory 136 and another computer system or a network using, for example, an Internet Protocol (IP) connection. These components may be conventional components such as those used in many conventional data processing systems, which may be configured to operate as described herein.

In particular, the processor 138 can be any commercially available or custom microprocessor, microcontroller, digital signal processor or the like. The memory 136 may include any memory devices containing the software and data used to implement the functionality circuits or modules used in accordance with embodiments of the present invention. The memory 136 can include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash memory, SRAM, DRAM and magnetic disk. In some embodiments of the present invention, the memory 136 may be a content addressable memory (CAM).

As further illustrated in FIG. 1, the memory 136 may include several categories of software and data used in the data processing system 100: an operating system 152; application programs 154; input/output device drivers 158; and data 156. As will be appreciated by those of skill in the art, the operating system 152 may be any operating system suitable for use with a data processing system, such as OS/2, AIX or zOS from International Business Machines Corporation, Armonk, N.Y., Windows95, Windows98, Windows2000 or WindowsXP from Microsoft Corporation, Redmond, Wash., Unix or Linux. The input/output device drivers 158 typically include software routines accessed through the operating system 152 by the application programs 154 to communicate with devices such as the input/output circuits 146 and certain memory 136 components. The application programs 154 are illustrative of the programs that implement the various features of the circuits and modules according to some embodiments of the present invention. Finally, the data 156 represents the static and dynamic data used by the application programs 154, the operating system 152, the input/output device drivers 158, and other software programs that may reside in the memory 136. As illustrated in FIG. 1, the data 156 may include standards 128 and test results 130 for use by the circuits and modules of the application programs 154 according to some embodiments of the present invention as discussed further herein.

As used herein, “standards” 128 refer to medical standards, such as ICD9, ICD10, SNOMED, LOINC and the like, local institution standards as well as any information that may be published in medical journal articles and the like. In particular, local institutions may have their own subset of standards that may specifically deal with things that they encounter more often than other institutions. For example, a cancer hospital may have more detailed standards codes for different types and symptoms of cancer because they see more cancer patients than other hospitals. Furthermore, the standards 128 may also include old standard protocols and names that have now been changed so that older diagnoses may also be included in results provided according to some embodiments of the present invention as will be discussed further herein. As used herein, “test results” 130 may include diagnostic test results, such as lab results, pathology reports, images (x-rays, MRIs etc.), physician's notes, and the like. The test results 130 may include both discrete data and semantic data without departing from the scope of the present invention.

Referring again to FIG. 1, according to some embodiments of the present invention the application programs 154 include a semantic module 126, a query generation module 124 and a learning module 122. The semantic module 126 may be configured to receive a diagnosis query from an external source, for example, a computing device being operated by a researcher or medical personnel. The semantic module 126 may be configured to receive diagnosis queries in multiple languages. In some embodiments of the present invention, the user (researcher or medical personnel) may be assigned a unique username and password. In these embodiments of the present invention, the semantic module 126 may be further configured to verify the user name and password before the user is allowed to make a diagnosis query. In some embodiments of the present invention, the username and password may be associated with a level of security clearance. Thus, each username and password may define what records a user making a diagnosis query can access. This can be used to keep highly confidential information in only a few hands. In some embodiments of the present invention, the security feature may be used to limit access to ones coworker's records. For example, a username and password of a nurse working at a particular hospital may indicate that this nurse cannot access the records of other employees at the same hospital. Thus, people's private information can be kept confidential from their coworkers.

The diagnosis query may be, for example, a discrete query or a semantic query. A discrete query may be, for example, a specific question such as “show me all patients diagnosed with breast cancer over the past ten year.” The “breast cancer” diagnosis may be expressed using a standards code for the diagnosis breast cancer, for example, it may be expressed in ICD9. A semantic query may be more complicated and may require more processing to determine exactly what is being asked as will be discussed further below.

For example, when the semantic module 126 receives a discrete diagnosis query like the example above, the semantic module 126 may be configured to provide the discrete diagnosis query to the query generation module 124. The query generation module 124 may be configured to determine what the code for breast cancer is in all 14 current medical standards. Then, all of the healthcare databases may be searched for each of the 14 codes and the results may be provided to the query generation circuit 124. The query generation circuit 124 may provide the query results to the user making the diagnosis query.

In some embodiments of the present invention, the query generation circuit 124 may be configured to provide the query results to the semantic module 126 before the results are provided to the user. For example, if the results are more complicated than just patients with breast cancer, the semantic module 126 may be configured to organize the query results and present them to the user in more user friendly format. For example, as discussed above, some embodiments of the present invention require a user name and password before a diagnosis query can be made. The semantic module 126 may be configured to display the query results in a particular way when this particular user name and password are used. For example, if the user name and password belong to an oncologist, all of the information in the query results associated with oncology may be displayed first.

In other words, the query generation module 124 is configured to parse the diagnosis query and provide the queries to standards databases and/or results databases to obtain the requested information. The semantic module 126 is configured to obtain the results provided by the query generation module 124 and format the results in a user friendly format.

The learning module 122 may be configured to learn from previously run diagnosis queries and modify the query results accordingly. Thus, each time a user runs a diagnosis query the learning module 122 learns something and adjusts the results of the next query accordingly. For example, a user may make a first diagnosis query and the query results may be provided to the user. Responsive to the query results, the user may provided a similar, but modified diagnosis query. The learning module may be configured to recognize this pattern and adjust the results of the next query so as to reduce the likelihood that the user will have to make the second modified query. Furthermore, in some embodiments of the present invention, the learning module may be configured to direct specific questions to the user to obtain information that may be used to fine tune future query results. For example, the learning module may be configured to ask the user “how close were the query results to what you wanted (0 to 100 percent)?” The user may specify a percentage, which the learning module 122 may be configured to use to modify future query results. Accordingly, the learning module 122 may implicitly learn from the actions taken by users of the query engine as well as from answers to specific questions posed by the learning module 122 without departing from the scope of the present invention.

While the present invention is illustrated with reference to the semantic module 126, the query generation module 124 and the learning module 122 being application programs in FIG. 1, as will be appreciated by those of skill in the art, other configurations fall within the scope of the present invention. For example, rather than being application programs 154, these modules may also be incorporated into the operating system 152 or other such logical division of the data processing system 100. Furthermore, while the semantic module 126, the query generation module 124 and the learning module 122 are illustrated in a single data processing system, as will be appreciated by those of skill in the art, such functionality may be distributed across one or more data processing systems. Thus, the present invention should not be construed as limited to the configuration illustrated in FIG. 1, but may be provided by other arrangements and/or divisions of functions between data processing systems. For example, although FIG. 1 is illustrated as having various circuits/modules, one or more of these circuits may be combined without departing from the scope of the present invention.

Referring now to FIG. 2, an exemplary environment 205 for operations and devices according to some embodiments of the present invention will be discussed. As illustrated in FIG. 2, the environment 205 may include a communications device 210, a network 220, a first server 240 and a second server 245. As illustrated, the communications device 210 illustrated in FIG. 2 may include the healthcare query module 100 according to some embodiments of the present invention discussed above with respect to FIG. 1. For example, the application programs 154 discussed with respect to FIG. 1 could be included as part of the healthcare query module 100 of the communications device 210. The communications device 210 may be, for example, a laptop computer, a desktop computer, a personal data assistant (PDA), a web capable mobile terminal or any device capable of communicating with the network 220. The communications device 210 may include a user interface 244, which may be used to enter diagnosis queries according to some embodiments of the present invention, a web browser 215 that may be accessed through the user interface 244, and a healthcare query module 200 according to some embodiments of the present invention. As discussed above, the healthcare query module 100 may be configured to receive diagnosis queries about one or more patients as discussed above with respect to FIG. 1. The first server 240 may include a standards database 230 including medical standards, such as ICD9, ICD10, LOINC, local standards and journal articles as discussed above with respect to FIG. 1. The second server 245 may include a test results database 235, which may include lab results, images, physician's notes and the like as discussed above with respect to FIG. 1. The communications device 210 may communicate over the network 220, for example, the Internet, through a telephone line, a digital subscriber link (DSL), a broadband cable link, a wireless link or the like. The first and second servers 240 and 245 may also communicate over the network 220. Thus, the network 220 may convey data between the communications device 210 and the first and second servers 240 and 245.

It will be understood that although only a single standards database 230 and a single test results database 235 are illustrated in FIG. 2, embodiments of the present invention are not limited to this configuration. For example, multiple standards databases and multiple test results databases can be included in the environment 205 without departing from the scope of the present invention. For example, there may be a standards database corresponding to each of the current medical standards, each of the local standards and each medical journal.

Exemplary data flows of a system including a healthcare query module according to some embodiments of the present invention will be discussed with respect to FIG. 3. As illustrated in FIG. 3, the system 300 includes a communication device 210, a healthcare query module 305 and external databases 330. The communications devices 210 may include a user interface 244 and a web browser 215 as discussed above with respect to FIG. 2. The healthcare query module 305 may include the semantic module 315, the query generation module 320 and the learning module 325. It will be understood that the healthcare query module 305 may be provided in the communications device 210 as illustrated in FIG. 2 or be separate from the communications device 210 without departing from the scope of the present invention. The external databases 330 may include the standards and/or test results databases as discussed above.

A user, for example, a doctor, may provide a diagnosis query 350 to the healthcare query module 305 according to some embodiments of the present invention. Before the healthcare query module 305 processes the diagnosis query 350, the healthcare query module 305 may verify a username and password provided by the doctor and determine the doctor's level of security clearance, i.e., which databases the doctor can access. As discussed above, the diagnosis query 350 may be a discrete query or a more complicated semantic query. Once the username and password are verified and the diagnosis query 350 is received at the healthcare query module 305, the query generation module 320 may parse the query to determine what information has been requested. For example, the query generation module 320 may find a LOINC code for breast cancer in the diagnosis query 350. Thus, the query generation module 320 may request the equivalent standards code in SNOMED, ICD9, ICD10 and the like from the standards databases (external databases 330). Once each of these codes has been identified, including outdated codes that have been given updated code names, the query generation module 320 may search the test results databases that the doctor has clearance access to for each of these codes.

Once the results of this search are received by the query generation module 320, query results 360 may be provided directly to the doctor at the communications device 210. However, in some embodiments of the present invention, the query generation module 320 may provide the query results 360 to the semantic module 315 before providing the results to the doctor. For example, the semantic module 315 may be configured to format the query results in accordance with user preferences associated with the username and password. For example, if the doctor is an oncologist, all of the oncology related results may be provided first. Once the semantic module 315 has formatted the query results 360, the query results 396 may be provided to the doctor.

In some embodiments of the present invention, the doctor may receive the results and then provide a modified diagnosis query 350 responsive to the query results 360. This may indicate to the healthcare query module 305 that the doctor was not totally satisfied with the query results 360. Thus, the learning module 325 may be configured to recognize a difference between the first and second queries and modify the next set of query results based on the what it learned from the difference. Thus, each time a query is made, the learning module 325 may learn something, which may be used to improve the query results associated with future diagnosis queries. In some embodiments of the present invention, the learning module 325 may be further configured to ask specific questions of the user, the answers to which can be used to fine tune future query results.

It will be understood that the exemplary operations discussed with respect to FIG. 3 are provided for exemplary purposes only and, therefore, embodiments of the present invention should not be limited to the specifics of the example discussed herein.

Operations according to various embodiments of the present invention will now be discussed with respect to the flowcharts of FIGS. 4 through 6. Operations for synthesizing diagnoses stored in healthcare databases begin at block 405 by receiving a diagnosis query associated with a single patient or a group of patients. The diagnosis query can be, for example, a discrete query and/or a semantic query. Query results are provided responsive to the diagnosis query (block 425). The query results include diagnoses from multiple sources, for example, multiple hospital databases, that are expressed in multiple standards formats, for example, LOINC, ICD9, ICD10 and the like. It will be understood that the diagnosis query may only specify a single standard code and the additional codes may be located according to some embodiments of the present invention.

Referring now to FIG. 5, operations begin at block 500 by verifying a username and password. Each user, for example, doctor or researcher, may have a unique username and level of security clearance. The level of security clearance may determine which information can be accessed by the user of the associated username and password. A diagnosis query associated with a single patient or a group of patients is received if the username and password are verified (block 505). It is determined if the diagnosis query includes a first standards code in conformance with a first standard therein (block 510). For example, the diagnosis query may include the ICD9 code for breast cancer. If it is determined that the diagnosis query includes a first standards code (block 510), equivalent standards codes to the first standards code are determined in conformance with at least one second standard, different from the first standard (block 520). For example, the corresponding LOINC, SNOMED, ICD10 etc. codes for breast cancer are determined. The query results are provided based on both the first standards code and the equivalent standards codes (block 525). Thus, all (or more than one) the breast cancer codes may be searched and the results with respect to each may be provided even though only a single code in conformance with a single standard is provided in the diagnosis query.

Query adjustments may be received from the user responsive to the query results provided (block 530). This may indicate that the user was not completely satisfied with the query results. Thus, future query results may be adjusted based on the received query adjustments (block 535). The future query results may also be adjusted based on user's answers to explicit questions without departing from the scope of the present invention.

Referring now to FIG. 6, operations begin at block 605 by by receiving a diagnosis query associated with a single patient or a group of patients. The diagnosis query may be processed to generate at least one modified diagnosis query that can be provided to external databases to obtain the query results (block 607). The at least one modified diagnosis query may be provided to at least one standards database and/or at least one diagnostic test results database (block 612). Intermediate query results may be received from the at least one standards database and/or the at least one diagnostic test results database (block 617). A format of the intermediate query results may be modified before providing the query results to a user (block 622). In some embodiments of the present invention, the query results may be modified/formatted based on a user profile and/or information obtained from previously received diagnosis queries and/or associated with a username and password. For example, if the user is an oncologist, all of the oncology related results may be provided first.

It will be understood that the circuits and other means supported by each block and combinations of blocks can be implemented by special purpose hardware, software or firmware operating on special or general purpose data processors, or combinations thereof. It should also be noted that, in some alternative implementations, the operations noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order.

Many alterations and modifications may be made by those having ordinary skill in the art, given the benefit of present disclosure, without departing from the spirit and scope of the invention. Therefore, it must be understood that the illustrated embodiments have been set forth only for the purposes of example, and that it should not be taken as limiting the invention as defined by the following claims. The following claims are, therefore, to be read to include not only the combination of elements which are literally set forth but all equivalent elements for performing substantially the same function in substantially the same way to obtain substantially the same result. The claims are thus to be understood to include what is specifically illustrated and described above, what is conceptually equivalent, and also what incorporates the essential idea of the invention. 

1. A method of synthesizing diagnoses stored in healthcare databases, comprising: receiving a diagnosis query associated with a single patient or a group of patients; and providing query results responsive to the diagnosis query, the query results including diagnoses from multiple sources that are expressed in multiple standards formats.
 2. The method of claim 1, wherein receiving is preceded by verifying a username and password associated with the username and wherein receiving further comprises receiving the diagnosis query only if the username and password are verified.
 3. The method of claim 2, wherein each username and associated password is associated with a level of security clearance, the level of security clearance determining which information can be accessed by a user of the associated username and password.
 4. The method of claim 1, wherein providing query results comprises: determining if the diagnosis query includes a first standards code in conformance with a first standard therein; determining equivalent standards codes to the first standards code in conformance with at least one second standard, different from the first standard, if it is determined that the diagnosis query includes a first standards code; and providing the query results based on both the first standards code and the equivalent standards codes.
 5. The method of claim 1, further comprising receiving query adjustments responsive to the provided query results.
 6. The method of claim 5, further comprising adjusting future query results based on the received query adjustments.
 7. The method of claim 1, wherein the received diagnosis query comprises a discrete query or a semantic query.
 8. The method of claim 1, wherein providing query results is preceded by processing the received diagnosis query to generate at least one modified diagnosis query that can be provided to external databases to obtain the query results.
 9. The method of claim 8, further comprising: providing the at least one modified diagnosis query to at least one standards database and/or at least one diagnostic test results database; receiving intermediate query results from the at least one standards database and/or the at least one diagnostic test results database; and modifying a format of the intermediate query results before providing the query results to a user.
 10. The method of claim 9, wherein modifying the format further comprises modifying the format based on a user profile and/or information obtained from previously received diagnosis queries.
 11. A system for synthesizing diagnoses stored in healthcare databases, comprising a healthcare query module configured to receive a diagnosis query associated with a single patient or a group of patients and provide query results responsive to the diagnosis query, the query results including diagnoses from multiple sources that are expressed in multiple standards formats.
 12. The system of claim 11, wherein the healthcare query module is further configured to verify a username and password associated with the username before receiving the diagnosis query and receive the diagnosis query only if the username and password are verified.
 13. The system of claim 12, wherein each username and associated password is associated with a level of security clearance, the level of security clearance determining which information can be accessed by a user of the associated username and password.
 14. The system of claim 11, wherein the healthcare query module comprises a query generation module, the query generation module being configured to: determine if the diagnosis query includes a first standards code in conformance with a first standard therein; determine equivalent standards codes to the first standards code in conformance with at least one second standard, different from the first standard, if it is determined that the diagnosis query includes a first standards code; and provide the query results based on both the first standards code and the equivalent standards codes.
 15. The system of claim 11, wherein the healthcare query module further comprises a learning module, the learning module being configured to receive query adjustments responsive to the provided query results.
 16. The system of claim 11, wherein the learning module is further configured to adjust future query results based on the received query adjustments.
 17. The system of claim 11, wherein the received diagnosis query comprises a discrete query or a semantic query.
 18. The system of claim 14, wherein the query generation module is further configured to process the received diagnosis query to generate at least one modified diagnosis query that can be provided to external databases to obtain the query results.
 19. The system of claim 18, wherein the query generation module if further configured to: provide the at least one modified diagnosis query to at least one standards database and/or at least one diagnostic test results database; receive intermediate query results from the at least one standards database and/or the at least one diagnostic test results database; and wherein the healthcare query module further comprises a semantic module, the semantic module being configured to modify a format of the intermediate query results before providing the query results to a user.
 20. The system of claim 19, wherein the semantic module is further configured to modify the format based on a user profile and/or information obtained from previously received diagnosis queries.
 21. A computer program product for synthesizing diagnoses stored in healthcare databases, comprising: computer readable storage medium having computer readable program code embodied in said medium, the computer readable program code comprising: computer readable program code configured to receive a diagnosis query associated with a single patient or a group of patients; and computer readable program code configured to provide query results responsive to the diagnosis query, the query results including diagnoses from multiple sources that are expressed in multiple standards formats.
 22. The computer program product of claim 21, further comprising computer readable program code configured to verify username and password associated with the username, wherein the computer readable program code configured to receive further comprises computer readable program code configured to receive the diagnosis query only if the username and password are verified.
 23. The computer program product of claim 22, wherein each username and associated password is associated with a level of security clearance, the level of security clearance determining which information can be accessed by a user of the associated username and password.
 24. The computer program product of claim 21, wherein the computer readable program code configured to provide query results comprises: computer readable program code configured to determine if the diagnosis query includes a first standards code in conformance with a first standard therein; computer readable program code configured to determine equivalent standards codes to the first standards code in conformance with at least one second standard, different from the first standard, if it is determined that the diagnosis query includes a first standards code; and computer readable program code configured to provide the query results based on both the first standards code and the equivalent standards codes.
 25. The computer program product of claim 21, further comprising computer readable program code configured to receive query adjustments responsive to the provided query results.
 26. The computer program product of claim 25, further comprising computer readable program code configured to adjust future query results based on the received query adjustments.
 27. The computer program product of claim 21, wherein the received diagnosis query comprises a discrete query or a semantic query.
 28. The computer program product of claim 21, further comprising computer readable program code configured to process the received diagnosis query to generate at least one modified diagnosis query that can be provided to external databases to obtain the query results.
 29. The computer program product of claim 28, further comprising: computer readable program code configured to provide the at least one modified diagnosis query to at least one standards database and/or at least one diagnostic test results database; computer readable program code configured to receive intermediate query results from the at least one standards database and/or the at least one diagnostic test results database; and computer readable program code configured to modify a format of the intermediate query results before providing the query results to a user.
 30. The computer program product of claim 29, wherein the computer readable program code configured to modify the format further comprises computer readable program code configured to modify the format based on a user profile and/or information obtained from previously received diagnosis queries. 